Skip to content

Conversation

@noraleonte
Copy link
Contributor

Closes #19494

@noraleonte noraleonte added the scope: scheduler Changes related to the scheduler. label Oct 27, 2025
@mui-bot
Copy link

mui-bot commented Oct 27, 2025

Deploy preview: https://deploy-preview-20108--material-ui-x.netlify.app/

Bundle size report

Bundle Parsed size Gzip size
@mui/x-data-grid 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-pro 0B(0.00%) 0B(0.00%)
@mui/x-data-grid-premium 0B(0.00%) 0B(0.00%)
@mui/x-charts 0B(0.00%) 0B(0.00%)
@mui/x-charts-pro 0B(0.00%) 0B(0.00%)
@mui/x-charts-premium 0B(0.00%) 0B(0.00%)
@mui/x-date-pickers 0B(0.00%) 0B(0.00%)
@mui/x-date-pickers-pro 0B(0.00%) 0B(0.00%)
@mui/x-tree-view 0B(0.00%) 0B(0.00%)
@mui/x-tree-view-pro 0B(0.00%) 0B(0.00%)

Details of bundle changes

Generated by 🚫 dangerJS against 0ff0f7e

@noraleonte noraleonte added the type: new feature Expand the scope of the product to solve a new problem. label Oct 27, 2025
@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged. label Oct 28, 2025
@github-actions
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged. label Oct 29, 2025
@noraleonte noraleonte marked this pull request as ready for review October 30, 2025 09:19
@github-actions github-actions bot added the PR: out-of-date The pull request has merge conflicts and can't be merged. label Oct 31, 2025
@github-actions
Copy link

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot removed the PR: out-of-date The pull request has merge conflicts and can't be merged. label Nov 3, 2025
Copy link
Member

@flaviendelangle flaviendelangle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One last feedback and we are good to go 👍

if (children) {
for (const child of children) {
if (!resourceChildrenIdLookup.get(processedResource.id)) {
resourceChildrenIdLookup.set(processedResource.id, []);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you should be able to generate resourceChildrenIdLookup in a selector instead of storing it in the state. It' just derived from processedResourceLookup right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, not sure we can 🤔 i separated the children ids resourceChildrenIdLookup and processedResourceLookup only keeps the resource data without its children nested 😬

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK we can keep it as is and refacto later if needs be 👍

@noraleonte noraleonte merged commit beea7d6 into mui:master Nov 10, 2025
21 checks passed
@noraleonte noraleonte deleted the nested-resources branch November 10, 2025 14:13
bernardobelchior added a commit to bernardobelchior/mui-x that referenced this pull request Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

scope: scheduler Changes related to the scheduler. type: new feature Expand the scope of the product to solve a new problem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[scheduler] Allow to have nested resources

3 participants